Offset optimization system

ABSTRACT

Systems, methods, and computer program products are provided for optimizing amounts collected in an offset action where a creditor garnishes funds from a debtor&#39;s deposits account to satisfy delinquent debt payments. In operation, embodiments of the present invention leverage a deposits account&#39;s transaction history to detect a deposit pattern for the account and, based on the detected pattern, predict the date of the next large deposit to the garnishable account. An offset associate, using the present invention, can then schedule the offset action to occur on the expected date of the next large deposit.

CROSS-REFERENCE TO RELATED APPLICATION

This application is a continuation of and claims priority from allowed,co-pending U.S. patent application Ser. No. 12/255,000, filed on Oct.21, 2008 and entitled “OFFSET OPTIMIZATION SYSTEM,” the entire contentsof which are incorporated herein by reference.

FIELD

In general, embodiments of the invention relate to systems, methods, andcomputer program products for optimizing amounts collected in an offsetaction where a creditor garnishes funds from a debtor's deposits accountto satisfy delinquent debt obligations.

BACKGROUND

In the event of an account delinquency, a typical credit-card agreementfor a small-business credit-card account grants the card-issuing bankthe right to garnish—without notice—the credit-card holder's funds heldin deposits at the card-issuing bank to pay off delinquent credit-cardbalances. This is commonly referred to as an “offset action.” An offsetaction is the last resort for a card-issuing bank in its effort tocollect payment towards a delinquent credit-card account. When asmall-business credit-card account meets the terms for an offset action,it is at the bank's discretion whether and when the offset action willbe executed. Notice to the card holder/guarantor is not required beforeexecuting the offset action.

When a delinquent small-business credit-card account enters theoffset-action process, a collection associate at the card-issuing banksearches for the deposits accounts that the small-business credit-cardholder/guarantor has in the card-issuing bank. Once the depositsaccounts are identified and the offset-action proposal is approved, thenext decision to be made is when to execute the offset action andthereby garnish funds from the deposits accounts. This offset-timingdecision is critical to maximize the final amount collected in an offsetaction because small-business deposits-account balances sometimes shift,either upwards or downwards, dramatically from day-to-day or even fromhour-to-hour.

Currently, there are two approaches for offset timing: (1) anupon-approval approach, and (2) the trigger-event approach. In theupon-approval approach, a collection associate can execute an offsetaction as soon as possible after the offset proposal is approved. Forexample, a collection associate accesses the delinquent card-holder'sdeposits account and—at no particular time—transfers the availablebalance or the credit-card delinquent amount, whichever is less, to thesmall-business credit-card account. The collection associate thenrecords the transfer as a payment towards the credit-card balance indelinquency. Because account-balance fluctuations are common and becausethe collection associate takes action as a matter of course, not at astrategically scheduled time, a deposits account may be at itslow-balance point when the offset action is taken. Accordingly, theupon-approval approach may miss a lot of funds that could have otherwisebeen collected and applied as a payment towards the credit-card balancein delinquency.

In the trigger-event approach, although approval of an offset proposalis required before a collection associate can execute an offset action,approval alone is not enough. The approval must be followed by a triggerevent before the offset action can be executed. Accordingly, in thisapproach, an offset action is triggered upon the occurrence of a triggerevent. For example, per the trigger-event approach, after offsetapproval, the collection associate monitors the day-end account balanceof the deposits account on a daily basis and executes an offset actiononly when the day-end account balance meets or exceeds a certainthreshold, e.g. a preset amount or a preset percentage of the delinquentcredit-card balance.

While this approach is more advanced than the upon-approval approach, asdescribed above, it still commonly results in sub-optimal offsetamounts. For example, a sub-optimal offset action occurs when a triggerevent triggers an offset action, but, after the trigger event, thecredit-card holder withdraws funds before the collection associate has achance to execute the offset action and garnish funds from the depositsaccount. Also, for example, per trigger-event approach, an offset actionmay never occur because the trigger event may never occur. For example,if a deposits-account balance never meets the preset threshold, theoffset action is never triggered.

Typically, a bank may only have one chance to execute an offset actionbecause, after the offset action, the delinquent consumer may withdrawall remaining funds (if any remain) and terminate its bankingrelationship with the bank. Accordingly, when executing an offsetaction, it is desirable to maximize the amount of funds garnished in asingle offset action. However, when applying known approaches,garnishing the maximum amount is difficult because customers'deposits-account balances frequently fluctuate, and it is difficult totime the offset action such that the offset action occurs when theaccount is at a high-point balance.

SUMMARY

Systems, methods, and computer program products are provided foroptimizing amounts collected in an offset action where a creditorgarnishes funds from a debtor's deposits account to satisfy delinquentdebt payments. In operation, embodiments of the present inventionleverage a deposits account's transaction history to detect a depositpattern for the deposits account and, based on the detected pattern,predict the date of the next large deposits to the garnishable depositsaccount. A collection associate, using the present invention, can thenschedule the offset action to occur on the expected date of the nextlarge deposits. Thus optimizing the amount of funds garnished by theoffset action.

BRIEF DESCRIPTION OF THE DRAWINGS

Having thus described embodiments of the invention in general terms,reference will now be made to the accompanying drawings, which are notnecessarily drawn to scale, and wherein:

FIG. 1 illustrates an environment in which the processes describedherein are implemented according to one embodiment of the invention;

FIG. 2 is a flow chart illustrating an exemplary process of detecting adeposit pattern, according to one embodiment of the present invention;

FIG. 3 is a screenshot illustrating an exemplary output provided by theoffset-processing system, according to one embodiment of the presentinvention;

FIG. 4 is a screenshot illustrating another exemplary output provided bythe offset-processing system, according to one embodiment of the presentinvention;

FIG. 5 is a flow chart illustrating an exemplary process for operatingthe offset-processing system, according to an embodiment of the presentinvention; and

FIG. 6 is a flow chart illustrating another exemplary process foroperating the offset-processing system, according to an embodiment ofthe present invention.

DETAILED DESCRIPTION OF EMBODIMENTS OF THE INVENTION

Embodiments of the present invention now will be described more fullyhereinafter with reference to the accompanying drawings, in which some,but not all, embodiments of the invention are shown. Indeed, theinvention may be embodied in many different forms and should not beconstrued as limited to the embodiments set forth herein, unless theclaims clearly indicate otherwise; rather, these embodiments areprovided so that this disclosure will satisfy applicable legalrequirements. Like numbers refer to like elements throughout. It shouldalso be appreciated that, although embodiments of the invention aregenerally described herein with regard to a bank that holds depositsaccounts and issues credit cards, other embodiments of the invention maybenefit individuals or business or non-business entities—other thanbanks—that hold deposits accounts and/or issue credit.

In general, embodiments of the present invention provide systems,methods, and computer program products for optimizing amounts collectedin an offset action where a creditor garnishes funds from a debtor'sdeposits account to satisfy delinquent debt payments. In operation,embodiments of the present invention leverage a deposits account'stransaction history to detect a deposit pattern for the account and,based on the detected pattern, predict the date of the next largedeposit to the garnishable deposits account. A collection associate,using the present invention, can then schedule the offset action tooccur on the expected date of the next large deposit.

FIG. 1 provides a block diagram illustrating an offset-collection system100, in accordance with one embodiment of the present invention. Asillustrated in FIG. 1, the offset-collection system 100 generallycomprises a creditor institution 104, a collection associate 108, and anoffset-processing system 112, all of which are communicably coupled viaa network 116.

In the illustrated embodiment, the creditor institution 104 offerscredit accounts 120 and deposits accounts 124 to debtors 128. Forillustrative convenience, the creditor institution 104 is describedherein as a bank that offers credit-card accounts and deposits accountsto small businesses. Also, for illustrative convenience, all of thecredit accounts 120 referred to herein are delinquent credit-cardaccounts and all of the deposits accounts 124 referred to herein havebeen deemed garnishable.

Accordingly, unless otherwise stated, the creditor institution 104 isreferred to herein as “the bank 104,” credit accounts 120 are referredto herein as “delinquent credit-card accounts 120,” deposits accounts124 are referred to herein as “garnishable deposits accounts 124,” anddebtors 128 are referred to herein as “small businesses 128.” It shouldbe appreciated, however, that the creditor institution 104 could be anyindividual or business or non-business entity that provides any knowntype of credit account 120 and/or deposits account 124 to debtors 128,which can be any individual or business or non-business entity.

In the illustrated embodiment, the bank 104, the collection associate108, and the offset-processing system 112 are separate entities. Thecollection associate 108 is a third-party entity that has access totransaction history relating to delinquent credit-card accounts 120 andgarnishable deposits accounts 124 held by the bank 104. Theoffset-processing system 112 is administered by another third-partyentity. In this example, the offset-processing system 112 also hasaccess to transaction history relating to delinquent credit-cardaccounts 120 and garnishable deposits accounts 124 held by the bank 104.What's more, the collection associate 108 has access to theoffset-processing system 112 such that the collection associate 108 cansend and receive information to and from the offset-processing system112.

It should be appreciated, however, that the collection associate 108could be part of the bank, and that the offset-processing system 112 canbe administered by the bank 104. It should also be appreciated that theoffset-processing system 112 and the collection associate 108 could beadministered by the same third-party entity.

In operation, according to an embodiment, the collection associate 108accesses the offset-processing system 112, via the terminal 132 tocreate bar charts that summarize the transaction history that comprisesdeposits and withdrawals made to and from garnishable deposits accounts124 and to generate a basic statement that indicates the expected dateof the next sizable deposit and/or the date on which frequent depositsare made. Next, the collection associate 108, using theoffset-processing system 112, schedules an offset action to occur on theexpected date of the next sizable deposit and/or the date on whichfrequent deposits are made. Instead of, or in addition to scheduling theoffset action, the collection associate 108 can use theoffset-processing system 112 to execute the offset action.

The illustrated offset-processing system 112 will now be described inmore detail. According to the illustrated embodiment, theoffset-processing system 112 includes a transaction-history retriever140, a deposit/withdrawal calculator 144, a deposit-pattern detector148, a data interpreter 152, and an offset-action executor 156.

The transaction-history retriever 140 accesses a transaction-historydatabase 160, which is maintained and updated by the bank 104, andretrieves transaction history for each of the garnishable depositsaccounts 124. For example, the transaction history includes depositsdata, such as the date and amount of money deposited into thegarnishable deposits accounts 124. The deposit/withdrawal calculator 144sifts through the transaction history and calculates the daily totaldeposits and withdrawal amounts for each of the garnishable depositsaccounts. Based on the daily total deposits and withdrawal amounts, thedeposit/withdrawal calculator calculates a daily net deposit amount.

The deposit-pattern detector 148 analyzes the transaction historyretrieved by the transaction-history retriever 140, and, for each of thegarnishable deposits accounts 124, the deposit-pattern detector 148detects a deposit pattern. For example, for any given garnishabledeposits account 124, the deposit-pattern detector 148 may detectfrequent and/or large deposits on a particular day(s) of the week and/ormonth, e.g., a deposit is made on Friday of each week or the last day ofeach month. The deposit-pattern detector 148 may also detect frequentand/or large deposits on a particular weekday(s) of each month, e.g., adeposit is made on the first Monday of each month.

Referring now to FIG. 2, exemplary operating procedures 200 for thedeposit-pattern detector 148 are provided. The exemplary operatingprocedures 200, when executed by the deposit-pattern detector 148,detect weekly deposit patterns that indicate which weekday(s) receivesthe most frequent deposits. It should be appreciated, however, thatoperating procedures could be configured to detect deposit pattern otherthan weekly deposit patterns. For example, procedures could be providedfor detecting monthly deposit patterns, which would indicate frequentdeposit(s) made on certain day(s) of the month, e.g., the last day ofthe month. Also for example, procedures could be provided for detectingmonthly weekday patterns. These patterns indicate frequent deposit(s)made on certain weekday(s) of each month, e.g., the first Monday of eachmonth.

The exemplary operating procedures 200 instruct the deposit-patterndetector 148 to first review the deposits made on each of the weekdays,and then compare the weekdays to determine which weekday(s) receives themost frequent and/or sizable deposits. As represented by block 204, theexemplary operating procedures 200 instruct the deposit-pattern detector148 to organize the daily deposits amounts, which are determined by thedeposit/withdrawal calculator 144, by weekday for the last four weeks.The exemplary operating procedures 200 instruct the deposit-patterndetector 148 to consider the last four complete weeks of transactiondata. However, it should be appreciated that other date-ranges could beconsidered.

Next, as represented by block 208, the exemplary operating procedures200 instruct the deposit-pattern detector 148 to calculate the averagedaily deposit amount for the last four weeks. For example, to do so, thedeposit-pattern detector 148 aggregates all of the deposits amounts ofthe last four weeks and divides that amount by twenty, i.e., the totalnumber of weekdays in a four-week period.

After calculating the average daily deposit amount, the exemplaryoperating procedures 200, as represented by block 212, instruct thedeposit-pattern detector 148 to select a weekday, e.g., Monday, andthen, as represented by block 216, review the transaction history forthe selected weekday to determine whether a deposit was made to thegarnishable deposits account 124 on the selected weekday in each of thelast four weeks. For example, if Monday is the selected weekday, thenthe deposit-pattern detector 148 reviews the transaction history of thelast four Mondays to determine whether a deposit was made on each of thelast four Mondays.

As represented by block 220, if a deposit was not made on each of theweekdays, the operating procedures advance to block 222, where thedeposit-pattern detector 148 determines if all of the weekdays, e.g.,Monday through Friday, have been selected. If all of the weekdays havenot been selected, the deposit-pattern detector 148 advances to block224 and selects another weekday, e.g., Tuesday. However, if all of theweekdays have been selected for review, the deposit-pattern detector 148advances to “END.”

If, at block 220, the deposit-pattern detector 148 determines that adeposit was made on the selected weekday in each of the last four weeks,then the deposit-pattern detector 148 advances to block 224. Here, thedeposit-pattern detector 148 reviews the deposit amounts made on theselected weekday in each of the last four weeks to identify the smallestdeposit amount made on the selected weekday.

Then, as represented by block 228, the deposit-pattern detector 148compares the identified smallest deposit amount to a preselected amount,e.g., $300. Next, at block 232, if the smallest deposit amount is lessthan the preselected amount, then the deposit-pattern detector 148returns to block 222. However, as represented by block 232, if thesmallest deposit amount is greater than the preselected amount, thedeposit-pattern detector 148 advances to block 236. Here, thedeposit-pattern detector 148 determines if the identified smallestdeposit amount is greater than the average daily deposit amount, whichwas determined at block 208.

As represented by block 240, if the smallest deposit amount is notgreater than the average daily deposits amount, then the deposit-patterndetector 148 returns to block 222. If, at block 240, the smallestdeposits amount is greater than the average daily deposits amount, thenthe deposit-pattern detector 148 advances to block 244. Here, thedeposit-pattern detector 148 sends to a final database 150 an indicationthat the selected weekday is a day when frequent and/or sizable depositsoccur and then returns to block 222.

Referring again to FIG. 1, the final database 150 is provided forreceiving and storing transaction history from the transaction historyretriever 140, daily total deposit and withdrawal amounts from thedeposit/withdrawal calculator 144, and detected deposit patterns, suchas an indication that frequent and/or sizable deposits are made on aparticular day of the week, from the deposit-pattern detector 148. Thedata interpreter 152 accesses the information stored in the finaldatabase 150 and, based thereon, creates bar charts that clearly presentthe transaction history of each garnishable deposits account 124, andthe data interpreter 152 translates the detected deposit patterns, whichare received from the deposit-pattern detector 148, into a basicstatement. Exemplary basic statements are provided below with referenceto FIGS. 3 and 4.

FIG. 3 provides an exemplary transaction-summary output 300, which isgenerated by the data interpreter 152 and presented to the collectionassociate 108 via the terminal 132. The transaction-summary output 300provides a summary of deposits and withdrawals that have been made toand from a garnishable deposits account 124 in the last four weeks. Thetransaction-summary output 300 provides an account number 304 and type308 (e.g., checking or savings) for the garnishable deposits account 124from which the funds are to be garnished. An account number 310 for thedelinquent small business credit card accounts 120, which is to beoffset by funds garnished from the garnishable deposits account 124, isalso provided.

A basic statement 316 —which, as mentioned above, is a translation ofthe detected deposit patterns—is included on the exemplarytransaction-summary output 300. For example, the basic statement 316 isa translation of the indication that the deposit-pattern detector 148sent to the final database 150 (see block 244 of FIG. 2). This basicstatement 316 is made available to the collection associate 108, so thatthe collection associate 108 can garnish funds at a time when frequentand/or sizable deposits are made to the garnishable deposits account124. For example, the illustrated basic statement 316 provides, “Thisaccount exhibited frequent deposits on Friday of a week.” Accordingly,the collection associate 108 can execute the offset and thereby garnishfunds from the garnishable deposits account 124 on a Friday.

The transaction-summary output 300 also provides a bar chart 320 thatwas created by the data interpreter 152 and that graphically illustratesdeposits and withdrawals made to and from a garnishable deposits account124. Bars 324, which extend upward from a horizontal axis 326, indicatedeposits made to the garnishable deposits account 124 and bars 328,which extend downward from the horizontal axis 326, indicatewithdrawals. The bar chart 320 provides side-by-side comparisons ofwithdrawals/deposits made on corresponding weekdays of the last fourweeks. For example, the bar chart 320 compares withdrawals/deposits madeon the last four Mondays to each other, withdrawals/deposits made on thelast four Tuesdays to each other, etc.

The illustrated bar chart 320 indicates that sizable deposits—relativeto the deposits made on other weekdays—were made on each of the lastfour Fridays. The fact that deposits were made on each of the last fourFridays indicates that deposits are frequently made on Fridays. The barchart 320 also indicates that relatively small withdrawals areinfrequently made on Fridays. What's more, the bar chart 320 indicatesthat only one sizeable withdrawal was made in the last four weeks.Accordingly, a collection associate 108 can review the bar chart 320 andquickly determine that, because sizable deposits are frequently made onFridays, Fridays could be ideal days to execute offset actions.

Referring now to FIG. 4, another exemplary transaction-summary output400 is illustrated. Like the exemplary transaction-summary output 300 ofFIG. 3, the exemplary transaction-summary output 400 provides an accountnumber 404 and type 408 for the garnishable deposits account 124 and anaccount number 410 for the delinquent small business credit-card account120.

The exemplary transaction-summary output 400 provides a summary ofdeposits and withdrawals that have been made to and from a garnishabledeposits account 124 in the last two months. The two months illustratedin FIG. 4 are January 2008, which has the last day of the month as day31, and February 2008, which has the last day of the month as day 29.Unlike the exemplary transaction-summary output 300 of FIG. 3, whichprovides side-by-side comparisons of withdrawals/deposits made oncorresponding weekdays of a month, the exemplary transaction-summaryoutput 400 includes a bar chart 420 that shows side-by-side comparisonsof withdrawals/deposits made on corresponding days of two months—inchronological order. For example, the first day of one month is comparedto the first day of the other month, the second day of one month iscompared to the second day of the other month, etc.

Bars 424, which indicate deposits, extend upward from a horizontal axis426, and bars 428, which indicate withdrawals, extend downward from thehorizontal axis 426. The illustrated bar chart 420 indicates thatsizable and/or frequent deposits were made on day 15 and last day of themonth. Also, a basic statement 416 is provided on the exemplarytransaction-summary chart 400 that describes, in plain English, thedeposit pattern detected by the deposit-pattern detector 148. Theillustrated basic statement 416 states, “This account exhibited frequentand/or sizable deposits on day 15 and the last day of a month.”

Taking into consideration all of the information provided from theexemplary transaction-summary output 400, the collection associate 108determines the appropriate day for executing the offset. The collectionassociate 108 may execute the offset on day 15 or the last day of themonth, which, according to the basic statement 416 and the bar chart420, are days when frequent and sizable deposits are made to thegarnishable deposits account 124. The decision of whether to garnishdeposits on day 15 or the last day of the month, in large part, dependson when the collection associate 108 receives offset approval from thebank 104.

For example, if the collection associate 108 receives offset approval onday 21 of the month, the collection associate 108 could wait and executethe offset action—and thereby garnish funds from the garnishabledeposits account 124—on the last day of the month. In addition togarnishing the funds in the offset action, because the bar chart 420shows a large withdrawal on the last day of one of the months, thecollection associate 108 could input, via the terminal 132, aninstruction to the bank 104 to allow only one-way transactions—depositsbut not withdrawals—for the garnishable deposits account 124. This wouldprevent a withdrawal from occurring before the funds are garnished.

Referring again to FIG. 1, when executing an offset action, thecollection associate 108 garnishes money from the garnishable depositsaccount 124 and then transfers the garnished money to the delinquentsmall business credit-card account 120. To execute the offset action,according to the illustrated embodiment, the collection associate 108accesses the offset-action executor 156 via the terminal 132. Theoffset-action executor 156 provides the collection associate 108 withaccess to the garnishable deposits account 124, which is held in thebank 104. The collection associate 108, using the offset-action executor156, then transfers the available balance or the credit-card delinquentamount, whichever less, from the garnishable deposits account 124 to thedelinquent small business credit-card account 120.

It should also be appreciated that, instead of actually executing theoffset action, the offset-action executor 156 schedules the offsetaction. For example, a collection associate 108, by way of theoffset-action executor 156 instructs the bank 104 to transfer funds fromthe garnishable deposits account 124 to the delinquent small businesscredit-card account 120 on a particular day, which is in the future.

Referring now to FIG. 5, an exemplary process 500 is provided thatillustrates operation of an exemplary offset-processing system 112. Theoffset-processing system 112, when executing the exemplary process 500,obtains and analyzes the transaction history of a garnishable depositsaccount 124, and, based thereon, detects a deposit pattern and indicatesto a collection associate 108 the day(s) when deposits are frequentlymade to the garnishable deposits account 124 so that the collectionassociate 108 can execute an offset action on that day(s).

As represented by block 504, the transaction-history retriever 140accesses the bank 104 to obtain a list of garnishable deposits accounts124. This list includes checking and savings accounts belonging to smallbusinesses 128 that have delinquent small business credit-card accounts120. In some embodiments, the bank 104 must authorize the offset actionbefore a particular garnishable deposits account 124 is included on thelist of garnishable deposits accounts. It should be appreciated that,instead of the transaction-history retriever 140 retrieving the list ofgarnishable deposits accounts 124, another component of theoffset-processing system 112 retrieves the list. It should also beappreciated that the collection associate 108 manually receives the listof garnishable deposits accounts 124 from the bank 104.

Next, as represented by block 508, the transaction-history retriever 140accesses the transaction-history database 160, which is maintained bythe bank 104, to retrieve transaction history for each of the listedgarnishable deposits accounts 124. For example, the transaction historyincludes a record of all deposits and withdrawals in the most recentmonths for the garnishable checking and savings accounts, including ACH,billpay, checks, teller transactions, ATM, wires, transfers, fees, etc.Then, as represented by block 512, the deposit/withdrawal calculator 144sifts through the transaction history for each of the garnishabledeposits accounts 124 and calculates the daily total deposits andwithdrawal amounts for each account.

As represented by block 516, the deposit-pattern detector 148 thendetects a weekly and/or monthly deposit pattern for each of thegarnishable deposits accounts 124. Next, as represented by block 520,the transaction-history retriever 140 sends the list of garnishabledeposits accounts 124 along with the associated transaction histories tothe final database 150. Also, as represented by 520, thedeposit/withdrawal calculator 144 sends daily total deposits andwithdrawal amounts to the final database 150, and the deposit-patterndetector 148 sends detected deposit patterns, such as which weekdayswhen deposits are frequently made, to the final database 150.

As represented by block 524, the data interpreter 152 accesses the finaldatabase 150 to obtain transaction data and detected deposit patternsfor the garnishable deposits account 124. The data interpreter 152 theninterprets the transaction data and the detected deposit patterns. Thisinterpretation is provided, for example, to the collection associate 108in the form of a basic statement that explains, in plain English, whichday(s) deposits are frequently made to the garnishable deposits account124. Also, for example, the interpretation is provided in the form ofbar charts that illustrate the deposits and withdrawals made to and fromthe garnishable deposits account 124 over a four-week period. Thecollection associate 108 then relies on the interpretations provided bythe data interpreter 152 when scheduling the offset action for a day onwhich deposits are frequently made to the garnishable deposits account.

Referring now to FIG. 6, another exemplary process 600 is provided thatillustrates operation of an exemplary offset-processing system 112. Theexemplary process 600 is provided for garnishing funds from agarnishable deposits account 124 to offset a delinquent small businesscredit-card account 120. In particular, the exemplary process 600enables a collection associate 108 to maximize the amount of fundsgarnished by scheduling the offset action for a day when deposits arefrequently made to the garnishable deposits account 124.

As represented by block 604, the collection associate 108 receives alist of garnishable deposits accounts 124 that the bank 104 has approvedas garnishable. For example, these garnishable deposits accounts 124belong to small businesses 128 that have delinquent small businesscredit-card accounts 120 with the bank 104. To determine the optimaltime to garnishing funds from the garnishable deposits accounts 124, thecollection associate 108 accesses the terminal 132 of theoffset-collection system 100 and, as represented by block 608, inputsthe list of garnishable deposits accounts 124.

As represented by block 612, the transaction history retriever 140accesses the transaction-history database 160 and retrieves transactionhistory for the listed garnishable deposits accounts 124. Next, asrepresented by block 616, the deposit-pattern detector 148 attempts todetect a deposit pattern for each of the listed garnishable depositsaccounts 124.

As represented by block 620, if a deposit pattern is detected, the datainterpreter 152 translates the detected deposit pattern into a basicstatement that indicates the day(s) deposits are frequently made (block624) and then the collection associate 108 accesses the offset-actionexecutor 156 to schedule the offset action for the day(s) indicated inthe basic statement (block 628). Referring again to block 620, if adeposit pattern is not detected, the data interpreter 152 creates barcharts illustrating the deposits and withdrawals (block 634) and thecollection associate 108 follows traditional offset time methods—such asthe upon-approval approach and the trigger-event approach, which aredescribed above—to schedule the offset action (block 638). Asrepresented by block 642, the offset-action executor 156 then executesthe offset action according to the schedule provided by the collectionassociate 108.

As will be appreciated by one of skill in the art, embodiments of theinvention may include a method (including a business process), system,computer program product, or a combination of the foregoing.Accordingly, embodiments of the present invention may take the form ofan entirely hardware embodiment, an entirely software embodiment(including firmware, resident software, micro-code, etc.), or anembodiment combining software and hardware aspects that may generally bereferred to herein as a “system.” Furthermore, embodiments of thepresent invention may take the form of a computer program product on acomputer-readable medium having computer-usable program code embodied inthe medium.

Any suitable computer-readable medium may be utilized. Thecomputer-readable medium may be, for example but not limited to, anelectronic, magnetic, optical, electromagnetic, infrared, orsemiconductor system, apparatus, device, or propagation medium. Morespecific examples of the computer-readable medium include, but are notlimited to, the following: an electrical connection having one or morewires; a tangible storage medium such as a portable computer diskette, ahard disk, a random access memory (RAM), a read-only memory (ROM), anerasable programmable read-only memory (EPROM or Flash memory), acompact disc read-only memory (CD-ROM), or other optical or magneticstorage device; or transmission media such as those supporting theInternet or an intranet. Note that the computer-readable medium couldeven be paper or another suitable medium upon which the program isprinted, as the program can be electronically captured, via, forinstance, optical scanning of the paper or other medium, then compiled,interpreted, or otherwise processed in a suitable manner, if necessary,and then stored in a computer memory.

In the context of this document, a computer-readable medium may be anymedium that can contain, store, communicate, propagate, or transport theprogram for use by or in connection with the instruction executionsystem, apparatus, or device. The computer-readable medium may include apropagated data signal with the computer-usable program code embodiedtherewith, either in baseband or as part of a carrier wave. Thecomputer-usable program code may be transmitted using any appropriatemedium, including but not limited to the Internet, wireline, opticalfiber cable, radio frequency (RF) signals, or other mediums.

Computer program code for carrying out operations of embodiments of thepresent invention may be written in an object oriented, scripted orunscripted programming language such as Java, Perl, Smalltalk, C++, orthe like. However, the computer program code for carrying out operationsof embodiments of the present invention may also be written inconventional procedural programming languages, such as the “C”programming language or similar programming languages.

Embodiments of the present invention are described below with referenceto flowchart illustrations and/or block diagrams of methods, apparatus(systems), and computer program products. It will be understood thateach block of the flowchart illustrations and/or block diagrams, and/orcombinations of blocks in the flowchart illustrations and/or blockdiagrams, can be implemented by computer program instructions. Thesecomputer program instructions may be provided to a processor of ageneral purpose computer, special purpose computer, or otherprogrammable data processing apparatus to produce a machine, such thatthe instructions, which execute via the processor of the computer orother programmable data processing apparatus, create means forimplementing the functions/acts specified in the flowchart and/or blockdiagram block or blocks.

These computer program instructions may also be stored in acomputer-readable memory that can direct a computer or otherprogrammable data processing apparatus to function in a particularmanner, such that the instructions stored in the computer-readablememory produce an article of manufacture including instruction meanswhich implement the function/act specified in the flowchart and/or blockdiagram block(s).

The computer program instructions may also be loaded onto a computer orother programmable data processing apparatus to cause a series ofoperational steps to be performed on the computer or other programmableapparatus to produce a computer-implemented process such that theinstructions which execute on the computer or other programmableapparatus provide steps for implementing the functions/acts specified inthe flowchart and/or block diagram block(s). Alternatively, computerprogram implemented steps or acts may be combined with operator or humanimplemented steps or acts in order to carry out an embodiment of theinvention.

While certain exemplary embodiments have been described and shown in theaccompanying drawings, it is to be understood that such embodiments aremerely illustrative of and not restrictive on the broad invention, andthat this invention not be limited to the specific constructions andarrangements shown and described, since various other changes,combinations, omissions, modifications and substitutions, in addition tothose set forth in the above paragraphs, are possible. Those skilled inthe art will appreciate that various adaptations and modifications ofthe just described embodiments can be configured without departing fromthe scope and spirit of the invention. Therefore, it is to be understoodthat, within the scope of the appended claims, the invention may bepracticed other than as specifically described herein.

1-36. (canceled)
 37. An apparatus for determining when to collect fundsfrom a deposits account, the apparatus comprising: a computer processorconfigured to: analyze a transaction history of deposits made to thedeposits account; detect a pattern in the transaction history ofdeposits; determine a suitable time to collect funds from the depositsaccount based at least partially on the pattern in the transactionhistory of deposits; and provide an indication of the suitable time tocollect funds from the deposits account.
 38. The apparatus of claim 37,wherein the computer processor is configured to: detect the pattern inthe transaction history of deposits based at least partially onfrequency of deposits; and determine the suitable time to be a time whendeposits are frequently made to the deposits account.
 39. The apparatusof claim 37, wherein the computer processor is configured to: detect thepattern in the transaction history of deposits based at least partiallyon size of deposits; and determine the suitable time to be a time whensizeable deposits are made to the deposits account.
 40. The apparatus ofclaim 37, wherein the computer processor is configured to: detect thepattern in the transaction history of deposits based at least partiallyon frequency of deposits and size of deposits; and determine thesuitable time to be a time when sizeable deposits are frequently made tothe deposits account.
 41. The apparatus of claim 37, wherein thecomputer processor is configured to: determine that past deposits arefrequently made to the deposits account at a particular point in timeduring each of a plurality of past recurring periods of time; anddetermine the suitable time to be the particular point in time duringthe next recurring period of time in the future.
 42. The apparatus ofclaim 41, wherein the recurring period of time comprises an hour, a day,a week, two weeks, a half month, or a month, and wherein the particularpoint in time comprises a minute, an hour, or a day.
 43. The apparatusof claim 37, wherein the computer processor is configured to: calculatea daily total deposit amount for the deposits account; and detect thepattern in the transaction history of deposits based on the daily totaldeposit amount.
 44. The apparatus of claim 37, wherein the computerprocessor is configured to: calculate a daily net deposit amount for thedeposits account by considering both deposits and withdrawals made tothe deposits account; and detect the pattern in the transaction historyof deposits based on the daily net deposit amount.
 45. The apparatus ofclaim 37, wherein the computer processor is configured to: determine aday of week or month on which deposits have been made with a frequencygreater than a particular threshold; determine a deposit amount based atleast partially on deposits made on the day of week or month over a pastone or more weeks or months; calculate an average daily deposit amountfor the deposits account over the past one or more weeks or months; anddetermine the suitable time to collect funds from the deposits accountbased at least partially on a comparison of the deposit amount and theaverage daily deposit amount.
 46. The apparatus of claim 37, furtherconfigured to determine when to garnish funds from the deposits account,wherein the deposit account is associated at least in part with a debtorowing funds to a creditor.
 47. The apparatus of claim 37, wherein thecomputer processor is configured to: provide the indication of thesuitable time by presenting the indication of the suitable time to auser.
 48. The apparatus of claim 37, wherein the computer processor isconfigured to: provide the indication of the suitable time by schedulingan automatic collection of funds from the deposits account based atleast partially on the indication of the suitable time.
 49. Theapparatus of claim 37, wherein the suitable time comprises a day in thefuture.
 50. The apparatus of claim 37, wherein the suitable timecomprises a day, a weekday, a day of week, a day of month, or aparticular date.
 51. The apparatus of claim 37, wherein the suitabletime comprises a time of day or a time of day on a particular day. 52.The apparatus of claim 37, wherein the computer processor is furtherconfigured to: display a bar chart to a user, the bar chart graphicallyillustrating deposits and withdrawals made to and from the depositsaccount and providing a side-by-side comparison of deposits andwithdrawals made on corresponding days of week or days of month over aplurality of past weeks or months.
 53. A method for determining when tocollect funds from a deposits account, the method comprising: analyzinga transaction history of deposits made to the deposits account;detecting, using a computer processor, a pattern in the transactionhistory of deposits; determining a suitable time to collect funds fromthe deposits account based at least partially on the pattern in thetransaction history of deposits; and providing an indication of thesuitable time to collect funds from the deposits account.
 54. The methodof claim 53, further comprising: detecting the pattern in thetransaction history of deposits based at least partially on frequency ofdeposits; and determining the suitable time to be a time when depositsare frequently made to the deposits account.
 55. The method of claim 53,further comprising: detecting the pattern in the transaction history ofdeposits based at least partially on frequency of deposits and size ofdeposits; and determining the suitable time to be a time when sizeabledeposits are frequently made to the deposits account.
 56. The method ofclaim 53, further comprising: determining a day of week on whichdeposits have been made with a frequency greater than a particularthreshold; determining a deposit amount based at least partially ondeposits made on the day of week over a past one or more weeks;calculating an average daily deposit amount for the deposits accountover the past one or more weeks; and determining the suitable time tocollect funds from the deposits account based at least partially on acomparison of the deposit amount and the average daily deposit amount.57. The method of claim 53, further comprising: determining a day ofmonth on which deposits have been made with a frequency greater than aparticular threshold; determining a deposit amount based at leastpartially on deposits made on the day of month over a past one or moremonths; calculating an average daily deposit amount for the depositsaccount over the past one or more months; and determining the suitabletime to collect funds from the deposits account based at least partiallyon a comparison of the deposit amount and the average daily depositamount.
 58. The method of claim 53, further comprising: garnishing fundsfrom the deposits account on the suitable time.
 59. The method of claim53, further comprising: providing the indication of the suitable time bypresenting the indication of the suitable time to a user.
 60. The methodof claim 53, wherein the suitable time comprises a day in the future.61. A computer program product for determining when to collect fundsfrom a deposits account, the computer program product comprising anon-transitory computer-readable medium having computer-readable programinstructions stored therein, wherein said computer-readable programinstructions comprise: first instructions configured for accessing atransaction history of deposits made to the deposits account; secondinstructions configured for detecting a pattern in the transactionhistory of deposits; third instructions configured for determining asuitable time to collect funds from the deposits account based at leastpartially on the pattern in the transaction history of deposits; andfourth instructions configured for providing an indication of thesuitable time to collect funds from the deposits account.
 62. Thecomputer program product of claim 61, further comprising: instructionsconfigured for detecting the pattern in the transaction history ofdeposits based at least partially on frequency of deposits; andinstructions configured for determining the suitable time to be a timewhen deposits are frequently made to the deposits account.
 63. Thecomputer program product of claim 61, further comprising: instructionsconfigured for detecting the pattern in the transaction history ofdeposits based at least partially on frequency of deposits and size ofdeposits; and instructions configured for determining the suitable timeto be a time when sizeable deposits are frequently made to the depositsaccount.
 64. The computer program product of claim 61, furthercomprising: instructions configured for determining a day of week onwhich deposits have been made with a frequency greater than a particularthreshold; instructions configured for determining a deposit amountbased at least partially on deposits made on the day of week over a pastone or more weeks; instructions configured for calculating an averagedaily deposit amount for the deposits account over the past one or moreweeks; and instructions configured for determining the suitable time tocollect funds from the deposits account based at least partially on acomparison of the deposit amount and the average daily deposit amount.65. The computer program product of claim 61, further comprising:instructions configured for determining a day of month on which depositshave been made with a frequency greater than a particular threshold;instructions configured for determining a deposit amount based at leastpartially on deposits made on the day of month over a past one or moremonths; instructions configured for calculating an average daily depositamount for the deposits account over the past one or more months; andinstructions configured for determining the suitable time to collectfunds from the deposits account based at least partially on a comparisonof the deposit amount and the average daily deposit amount.
 66. Thecomputer program product of claim 61, further comprising: instructionsconfigured for initiating collection of funds from the deposits accountat the suitable time.
 67. The computer program product of claim 61,further comprising: instructions configured for providing the indicationof the suitable time by presenting the indication of the suitable timeto a user.
 68. The computer program product of claim 61, wherein thesuitable time comprises a day in the future.
 69. The computer programproduct of claim 61, further comprising: instructions for displaying abar chart to a user, the bar chart graphically illustrating deposits andwithdrawals made to and from the deposits account and providing aside-by-side comparison of deposits and withdrawals made oncorresponding days of week or days of month over a plurality of pastweeks or months.